Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add initial projectsetup checklist for native android projects #9

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

stefanoberdoerfer
Copy link

This is our first draft for a checklist for all relevant steps to setup a new native Android project. As you can see, there are some leftover todos which will be worked on in the next weeks.

1. Create an empty base project in Android Studio.
1. Configure build types for different environments.
- TODO: List all build types (develop, staging, production) and add basic gradle snippets to template repo
2. Create a signing keystore for release builds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is best practise here? Do we have separate keystores per environment (e.g. staging, production) or is it safe to share the keystore in multiple environments (except production obviously)

1. Configure build types for different environments.
- TODO: List all build types (develop, staging, production) and add basic gradle snippets to template repo
2. Create a signing keystore for release builds.
3. Upload the necessary files and passwords to a secure password manager like 1Password.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not like 1Password. 1Password. We are using this and only this :)

3. Upload the necessary files and passwords to a secure password manager like 1Password.
2. Configure analytics, crash reporting, and static file analysis tools.
- TODO: add details for each step
1. Integrate Sentry for error tracking.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please link to sentry index docs. Might be helpful here.

2. Configure analytics, crash reporting, and static file analysis tools.
- TODO: add details for each step
1. Integrate Sentry for error tracking.
2. Use SonarCloud for code quality analysis.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please link to sonarcloud index docs. Might be helpful here.

- TODO: add details for each step
1. Integrate Sentry for error tracking.
2. Use SonarCloud for code quality analysis.
3. Configure Android Lint for static code analysis.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reference to the configuration ruleset?

@dasheck0
Copy link
Member

Already gave some review. Hope it helps. Also make sure that this is correctly linked to existing documents. It should be reachable by clicking links from the main document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants